Moving objects and containers: the Change locations task

Tasks guide users through a procedure that updates the current recordClosed The record currently displayed in Record details View or highlighted (with a solid background) in Result set View or Gallery View for instance. or markedClosed Marking a record means selecting it by adding a tick to the record's checkbox in Result set View or Gallery View, and in Record Details View from Collections 1.15 onwards. One or more records can be marked and then actioned in some way (e.g. printed). records in some way. The Change locations task is designed to update the current location and location history of one or more objects or containers and it is found in Catalogue data sources (for relocating collection items) and Locations and containers (for relocating containers). If available in your system, the Change locations task is accessed with the Tasks button in the Result set View toolbar:

Tasks

When more than one task is available, the Tasks button is a drop list of options:

When we create a record for an object in the Catalogue or for a container in Locations and containers we document a Normal Location, which is the item's default location (where it belongs and is typically found), and a Current location, which is where it is presently. These two locations will be the same if the object or container is currently in its Normal location, or different if it has been relocated for some reason.

While Normal Location can be edited at any time, Current location is read-only as soon as the Catalogue or Locations and containers record is saved. Subsequently, the Change locations task is the recommended method for documenting the relocation of objects and containers and updating their Current location. The Change locations task prompts users for all required information, ensures that all affected records are updated and a full history of location changes is maintained by the system.

Documenting locations and containers is similar across Model Applications and the key panels and fields available in Model Application 5.2 (and earlier) and the Standard Model are largely the same; there are some differences however and we document the workflows separately below: